<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<LINK REL="stylesheet" HREF="../../../style.css">
 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.50">
 <TITLE>DOMjudge Administrator's Manual: Team Workstations</TITLE>
 <LINK HREF="admin-manual-5.html" REL=next>
 <LINK HREF="admin-manual-3.html" REL=previous>
 <LINK HREF="admin-manual.html#toc4" REL=contents>
</HEAD>
<BODY>
<A HREF="admin-manual-5.html">Next</A>
<A HREF="admin-manual-3.html">Previous</A>
<A HREF="admin-manual.html#toc4">Contents</A>
<HR>
<H2><A NAME="teamworkstations"></A> <A NAME="s4">4.</A> <A HREF="admin-manual.html#toc4">Team Workstations</A></H2>


<P>Here's a quick checklist for configuring the team workstations. Of course,
when hosting many teams, it makes sense to generate a preconfigured account that
has these features and can be distributed over the workstations.</P>
<P>
<OL>
<LI> The central tool teams use to interact with DOMjudge is the web browser.
<UL>
<LI> If possible, set the Home Page to <CODE>your.domjudge.location/team/</CODE></LI>
<LI> Go to the team page and check if this team is correctly identified.</LI>
<LI> If using https and a self signed certificate, add this certificate
to the browser certificate list to prevent annoying dialogs.</LI>
</UL>
</LI>
<LI> Make sure compilers for the supported languages are installed and working.</LI>
<LI> Provide teams with the command line submit client and check that it works.</LI>
<LI> Make the sample in- and output data from the problem set available.</LI>
<LI> Add your SSH key to their authorized_keys file, so you can always access
their account for wiping and emergencies.</LI>
<LI> Check that internet access is blocked.</LI>
</OL>
</P>

<HR>
<A HREF="admin-manual-5.html">Next</A>
<A HREF="admin-manual-3.html">Previous</A>
<A HREF="admin-manual.html#toc4">Contents</A>
</BODY>
</HTML>
